Provision gpsi pertaining to pdu session(s)

ABSTRACT

Disclosed herein is a method by an AMF node 120-4 operative in a 5GS that comprises a UE 112 associated with a Subscriber Permanent Identifier (SUPI) that is associated with subscription data of the UE. The method comprises: sending towards a SMF node, a request relating to a PDU Session of the UE and comprising a Request Type that is set to Existing PDU Session; and receiving from the SMF node, a response comprising a 
     Generic Public Subscription Identifier (GPSI) of the PDU session, which GPSI is associated with the SUPI and which GPSI is to be used in networks outside the 5GS for addressing the subscription data of the UE.

This application is a continuation of U.S. patent application Ser. No.17/607,752, filed Oct. 29, 2021, which is a 35 U.S.C. § 371 nationalphase filing of International Application No. PCT/EP2020/061382, filedApr. 23, 2020, which claims the benefit of Provisional PatentApplication Ser. No. 62/842,309, filed May 2, 2019, the disclosures ofwhich are hereby incorporated herein by reference in their entireties.

BACKGROUND

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features,and advantages of the enclosed embodiments will be apparent from thefollowing description.

In the Third Generation Partnership Project (3GPP) Fifth Generation (5G)core (5GC), a User Equipment (UE) may have multiple General PublicSubscription Identifiers (GPSIs) associated to the same SubscriptionPermanent Identifier (SUPI).

As specified in 3GPP Technical Specification (TS) 23.501 V16.0.2:

5.9.8 Generic Public Subscription Identifier Generic Public SubscriptionIdentifier (GPSI) is needed for addressing a 3GPP subscription indifferent data networks outside of the 3GPP system. The 3GPP systemstores within the subscription data the association between the GPSI andthe corresponding SUPI. GPSIs are public identifiers used both insideand outside of the 3GPP system. The GPSI is either an MSISDN or anExternal Identifier, see TS 23.003 [19]. If MSISDN is included in thesubscription data, it shall be possible that the same MSISDN value issupported in both 5GS and EPS. NOTE: There is no implied 1-to-1relationship between GPSI and SUPI.

As specified in 3GPP TS 29.503 V15.3.0:

Type: AccessAndMobilitySubscriptionData

TABLE 6.1.6.2.4-1 Definition of type AccessAndMobilitySubscriptionDataAttribute name Data type P Cardinality Description supportedFeaturesSupportedFeatures O 0 . . . 1 See subclause 6.1.8 gpsis array(Gpsi) O 0. . . N List of Generic Public Subscription Identifier; see 3GPP TS29.571 [7] internalGroupIds array(GroupId) O 1 . . . N List of internalgroup identifier; see 3GPP TS 23.501 [2] subclause 5.9.7 . . . skippedthe rest for clarity . . .

The UE may acquire the following configuration information from theSession Management Function (SMF) during the lifetime of a Protocol DataUnit (PDU) Session:

-   -   address(es) of the Proxy Call Session Control Function (s)        (P-CSCF(s));    -   address(es) of Domain Name System (DNS) server(s); and    -   the GPSI of the UE.

SUMMARY

There currently exist certain challenge(s). The Access and MobilityManagement Function (AMF) only knows, for a given SUPI for a UE, a listof GPSI(s). This is insufficient, e.g., to support Lawful Interception(LI), as specified in 3GPP TS 33.127 V15.1.0, subclause 6.2.2.2, asbelow:

6.2.2.2 Target identities The LIPF present in the ADMF provisions theintercept information associated with the following target identities tothe IRI-POI present in the AMF:  - SUPI.  - PEI.  - GPSI. Theinterception performed on the above three identities are mutuallyindependent, even though, an xIRI may contain the information about theother identities when available.

In the case when a UE has multiple GPSIs, a PDU session activated by UEmay be linked to only one of GPSI. This means that only the signalingand/or user plane traffic applicable to this GPSI, i.e. the PDU sessionlinked to this GPSI, shall be intercepted, but NOT others.

The AMF is to know, for a given PDU session(s) from a UE (identified bya SUPI), which GPSI is associated with which PDU session(s).

Certain aspects of the present disclosure and their embodiments mayprovide solutions to the aforementioned or other challenges. In someembodiments, a mechanism is provided in 5GC to provision a GPSI,applicable to certain PDU session, from the (Home) Session ManagementFunction (SMF) ((h)SMF) to the (v-SMF) and/or AMF, viaSMContextCreatedData and/or PduSessionCreatedData.

There are, proposed herein, various embodiments which address one ormore of the issues disclosed herein. As depicted in FIGS. 4, 5, and 6and described below, in some embodiments, the present disclosureprovides a method performed by a Network Function (NF) (e.g., SMF, e.g.a SMF in the Home PLMN, i.e. a H-SMF) comprising receiving (WT300,XX100, XX200) a request from a NF service consumer, the request beingrelated to a PDU session and then sending (WT302, XX102A, XX202A) aresponse to the NF services consumer, the response comprising a GPSI ofthe PDU session. In at least one embodiment, such as shown in FIG. 5 ,the method comprises an SMF receiving (XX100) a request from the NFservice consumer requesting creation of an SM context. If the SM contextis successfully created, the method continues by sending (XX102A) amessage from the SMF to the NF service consumer that the SM context wascreated. Alternatively, if an error in creating the SM context occurs,the method continues by sending (XX102B) an error message from the SMFto the NF service consumer. Note that for an existing PDU session, e.g.PDU session moved from another access or another system, if a GPSI isassociated with the PDU session, the SMF includes the associated GPSI inthe response body (in step XX102A). For example, a PDU sessionconsidered as existing may be moved from EPS to 5GS. Also, for anexisting HR PDU session, if the GPSI associated with the PDU session isreceived from H-SMF in PDU Session Create response, the SMF includes itin the response body.

In at least one other embodiment, such as shown in FIG. 6 , the methodcomprises an H-SMF receiving (XX200) a request from the NF serviceconsumer requesting creation of a PDU session. If the PDU session issuccessfully created, the method continues by sending (XX202A) a messagefrom the H-SMF to the NF service consumer that the PDU session wascreated. Alternatively, if an error in creating the PDU session occurs,the method continues by sending (XX202B) an error message from the H-SMFto the NF service consumer. Note that for an existing PDU session, e.g.PDU session moved from another access or another system, if a GPSI isassociated with the PDU session, the SMF includes it in the responsebody.

A particular embodiment is directed to a method by an Access andMobility Management Function (AMF) node operative in a Fifth GenerationSystem (5GS) that comprises a User Equipment (UE) associated with aSubscriber Permanent Identifier (SUPI) that is associated withsubscription data of the UE. The method comprises: sending towards aSession Management Function (SMF) node, a request relating to a ProtocolData Unit (PDU) Session of the UE and comprising a Request Type that isset to Existing PDU Session; and receiving from the SMF node, a responsecomprising a Generic Public Subscription Identifier (GPSI) of the PDUsession, which GPSI is associated with the SUPI and which GPSI is to beused in networks outside the 5GS for addressing the subscription data ofthe UE.

Another particular embodiment is directed to a method by a SessionManagement Function (SMF) node operative in a Fifth Generation System(5GS) that comprises a User Equipment (UE) associated with a SubscriberPermanent Identifier (SUPI) that is associated with subscription data ofthe UE. The method comprises: receiving from an Access and MobilityManagement Function (AMF) node, a request relating to a Protocol DataUnit (PDU) Session of the UE and comprising a Request Type that is setto Existing PDU Session; and sending towards the AMF node, a responsecomprising a Generic Public Subscription Identifier (GPSI) of the PDUsession, which GPSI is associated with the SUPI and which GPSI is to beused in networks outside the 5GS for addressing the subscription data ofthe UE.

Another particular embodiment is directed to a network node implementingan Access and Mobility Management Function (AMF) node configured to beoperative in a Fifth Generation System (5GS) that comprises a UserEquipment (UE) associated with a Subscriber Permanent Identifier (SUPI)that is associated with subscription data of the UE. The AMF nodecomprises: a network interface; and processing circuitry associated withthe network interface. The processing circuitry is configured to causethe network node to implement the AMF node, the AMF node adapted to:send towards a Session Management Function (SMF) node, a requestrelating to a Protocol Data Unit (PDU) Session of the UE and comprisinga Request Type that is set to Existing PDU Session; and receive from theSMF node, a response comprising a Generic Public Subscription Identifier(GPSI) of the PDU session, which GPSI is associated with the SUPI andwhich GPSI is to be used in networks outside the 5GS for addressing thesubscription data of the UE.

Another particular embodiment is directed to a network node implementinga Session Management Function (SMF) node configured to be operative in aFifth Generation System (5GS) that comprises a User Equipment (UE)associated with a Subscriber Permanent Identifier (SUPI) that isassociated with subscription data of the UE. The network node comprises:a network interface; and processing circuitry associated with thenetwork interface. The processing circuitry is configured to cause thenetwork node to implement the SMF node, the SMF node adapted to: receivefrom an Access and Mobility Management Function (AMF) node, a requestrelating to a Protocol Data Unit (PDU) Session of the UE and comprisinga Request Type that is set to Existing PDU Session; and send to the AMFnode, a response comprising a GPSI of the existing PDU session, whichGPSI is associated with the SUPI and which GPSI is to be used innetworks outside the 5GS for addressing the subscription data of the UE.

Certain embodiments may provide one or more of the following technicaladvantage(s). The disclosure enables the AMF to know the exact GPSI,among a list of GPSIs for a UE (identified by a SUPI), to be associatedwith a PDU session.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the disclosure and are incorporated in and constitute apart of this application, illustrate certain non-limiting embodiments ofinventive concepts. In the drawings:

FIG. 1 illustrates one example of a cellular communications network100-1 according to some embodiments of the present disclosure;

FIG. 2 a illustrates a wireless communication system represented as anexemplifying Evolved Packet System (EPS) architecture comprising a RadioAccess Network (RAN) in the form of an Evolved Universal TerrestrialRadio Access Network (E-UTRAN) and a core network in the form of aEvolved Packet Core (EPC);

FIG. 2 b illustrates a wireless communication system 100-2 representedas a Fifth Generation (5G) System (5GS) architecture;

FIG. 3 illustrates a 5G System architecture 100-3 using service-basedinterfaces;

FIG. 4 illustrates the operation of a NF service producer and a NFservice consumer in accordance with some embodiment of the presentdisclosure;

FIG. 5 discloses a method to create an SM context by using the HTTP POSTmethod;

FIG. 6 illustrates a procedure for creating a PDU session;

FIG. 7 is a schematic block diagram of a network node according to someembodiments of the present disclosure;

FIG. 8 a schematic block diagram that illustrates a virtualizedembodiment of the network node according to some embodiments of thepresent disclosure;

FIG. 9 is a schematic block diagram of the network node QQ200 accordingto some other embodiments of the present disclosure.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described morefully with reference to the accompanying drawings. Other embodiments,however, are contained within the scope of the subject matter disclosedherein, the disclosed subject matter should not be construed as limitedto only the embodiments set forth herein; rather, these embodiments areprovided by way of example to convey the scope of the subject matter tothose skilled in the art. Additional information may also be found inthe document(s) provided in the Appendix.

Radio Node: As used herein, a “radio node” is either a radio access nodeor a wireless device.

Radio Access Node: As used herein, a “radio access node” or “radionetwork node” is any node in a radio access network of a cellularcommunications network that operates to wirelessly transmit and/orreceive signals. Some examples of a radio access node include, but arenot limited to, a base station (e.g., a New Radio (NR) base station(gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation(5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP LongTerm Evolution (LTE) network), a high-power or macro base station, alow-power base station (e.g., a micro base station, a pico base station,a home eNB, or the like), and a relay node.

Core Network Node: As used herein, a “core network node” is any type ofnode in a core network or any node that implements a core networkfunction. Some examples of a core network node include, e.g., a MobilityManagement Entity (MME), a Packet Data Network Gateway (PGW), a ServiceCapability Exposure Function (SCEF), a Home Subscriber Server (HSS), orthe like. Some other examples of a core network node include a nodeimplementing a Access and Mobility Function (AMF), a User Plane Function(UPF), a Session Management Function (SMF), an Authentication ServerFunction (AUSF), a Network Slice Selection Function (NSSF), a NetworkExposure Function (NEF), a Network Repository Function (NRF), a PolicyControl Function (PCF), a Unified Data Management (UDM), or the like.

Wireless Device: As used herein, a “wireless device” is any type ofdevice that has access to (i.e., is served by) a cellular communicationsnetwork by wirelessly transmitting and/or receiving signals to a radioaccess node(s). Some examples of a wireless device include, but are notlimited to, a User Equipment device (UE) in a 3GPP network and a MachineType Communication (MTC) device.

Network Node: As used herein, a “network node” is any node that iseither part of the radio access network or the core network of acellular communications network/system.

Note that the description given herein focuses on a 3GPP cellularcommunications system and, as such, 3GPP terminology or terminologysimilar to 3GPP terminology is oftentimes used. However, the conceptsdisclosed herein are not limited to a 3GPP system.

Note that, in the description herein, reference may be made to the term“cell”; however, particularly with respect to 5G NR concepts, beams maybe used instead of cells and, as such, it is important to note that theconcepts described herein are equally applicable to both cells andbeams.

FIG. 1

FIG. 1 illustrates one example of a cellular communications network100-1 according to some embodiments of the present disclosure. In theembodiments described herein, the cellular communications network 100-1is a 5G NR network. In this example, the cellular communications network100-1 includes base stations 102-1 and 102-2, which in LTE are referredto as eNBs and in 5G NR are referred to as gNBs, controllingcorresponding macro cells 104-1 and 104-2. The base stations 102-1 and102-2 are generally referred to herein collectively as base stations 102and individually as base station 102. Likewise, the macro cells 104-1and 104-2 are generally referred to herein collectively as macro cells104 and individually as macro cell 104. The cellular communicationsnetwork 100-1 may also include a number of low power nodes 106-1 through106-4 controlling corresponding small cells 108-1 through 108-4. The lowpower nodes 106-1 through 106-4 can be small base stations (such as picoor femto base stations) or Remote Radio Heads (RRHs), or the like.Notably, while not illustrated, one or more of the small cells 108-1through 108-4 may alternatively be provided by the base stations 102.The low power nodes 106-1 through 106-4 are generally referred to hereincollectively as low power nodes 106 and individually as low power node106. Likewise, the small cells 108-1 through 108-4 are generallyreferred to herein collectively as small cells 108 and individually assmall cell 108. The base stations 102 (and optionally the low powernodes 106) are connected to a core network 110-1.

The base stations 102 and the low power nodes 106 provide service towireless devices 112-1 through 112-5 in the corresponding cells 104 and108. The wireless devices 112-1 through 112-5 are generally referred toherein collectively as wireless devices 112 and individually as wirelessdevice 112. The wireless devices 112 are also sometimes referred toherein as UEs.

FIG. 2 a

FIG. 2 a illustrates a wireless communication system represented as anexemplifying Evolved

Packet System (EPS) architecture comprising a RAN in the form of anEvolved Universal Terrestrial Radio Access Network (E-UTRAN) and a corenetwork in the form of a Evolved Packet Core (EPC). The EPC comprisescore network nodes such as the Mobility Management Entity (MME), HomeSubscriber Server (HSS), Serving Gateway (SGW), PDN Gateway (PGW) andPolicy and Charging Rules Function (PCRF).

FIG. 2 b

FIG. 2 b illustrates a wireless communication system 100-2 representedas a 5G System architecture composed of core Network Functions (NFs),where interaction between any two NFs is represented by a point-to-pointreference point/interface. FIG. 2 b can be viewed as one particularimplementation of the system 100-1 of FIG. 1 .

Seen from the access side the 5G network architecture shown in FIG. 2 bcomprises a plurality of User Equipment (UEs) connected to either aRadio Access Network (RAN) or an Access Network (AN) as well as anAccess and Mobility Management Function (AMF). Typically, the R(AN)comprises base stations, e.g. such as evolved Node Bs (eNBs) or 5G basestations (gNBs) or similar. Seen from the core network side, the 5G coreNFs shown in FIG. 2 b include a Network Slice Selection Function (NSSF),an Authentication Server Function (AUSF), a Unified Data Management(UDM), an AMF, a Session Management Function (SMF), a Policy ControlFunction (PCF), and an Application Function (AF).

Reference point representations of the 5G network architecture are usedto develop detailed call flows in the normative standardization. The N1reference point is defined to carry signaling between the UE and AMF.The reference points for connecting between the AN and AMF and betweenthe AN and UPF are defined as N2 and N3, respectively. There is areference point, N11, between the AMF and SMF, which implies that theSMF is at least partly controlled by the AMF. N4 is used by the SMF andUPF so that the UPF can be set using the control signal generated by theSMF, and the UPF can report its state to the SMF. N9 is the referencepoint for the connection between different UPFs, and N14 is thereference point connecting between different AMFs, respectively. N15 andN7 are defined since the PCF applies policy to the AMF and SMP,respectively. N12 is required for the AMF to perform authentication ofthe UE. N8 and N10 are defined because the subscription data of the UEis required for the AMF and SMF.

The 5G core network aims at separating user plane and control plane. Theuser plane carries user traffic while the control plane carriessignaling in the network. In FIG. 2 b , the UPF is in the user plane andall other NFs, i.e., the AMF, SMF, PCF, AF, AUSF, and UDM, are in thecontrol plane. Separating the user and control planes guarantees eachplane resource to be scaled independently. It also allows UPFs to bedeployed separately from control plane functions in a distributedfashion. In this architecture, UPFs may be deployed very close to UEs toshorten the Round Trip Time (RTT) between UEs and data network for someapplications requiring low latency.

The core 5G network architecture is composed of modularized functions.For example, the AMF and SMF are independent functions in the controlplane. Separated AMF and SMF allow independent evolution and scaling.Other control plane functions like the PCF and AUSF can be separated asshown in FIG. 2 b . Modularized function design enables the 5G corenetwork to support various services flexibly.

Each NF interacts with another NF directly. It is possible to useintermediate functions to route messages from one NF to another NF. Inthe control plane, a set of interactions between two NFs is defined asservice so that its reuse is possible. This service enables support formodularity. The user plane supports interactions such as forwardingoperations between different UPFs.

FIG. 3

FIG. 3 illustrates a 5G System architecture 100-3 using service-basedinterfaces between the NFs in the control plane, instead of thepoint-to-point reference points/interfaces used in the 5G Systemarchitecture of FIG. 2 b . However, the NFs described above withreference to FIG. 2 b correspond to the NFs shown in FIG. 3 . Theservice(s) etc. that a NF provides to other authorized NFs can beexposed to the authorized NFs through the service-based interface. InFIG. 3 the service based interfaces are indicated by the letter “N”followed by the name of the NF, e.g. Namf for the service basedinterface of the AMF and Nsmf for the service based interface of the SMFetc. The Network Exposure Function (NEF) and the Network RepositoryFunction (NRF) in FIG. 3 are not shown in FIG. 2 b discussed above.However, it should be clarified that all NFs depicted in FIG. 2 b caninteract with the NEF and the NRF of FIG. 1 as necessary, though notexplicitly indicated in FIG. 2 b.

Some properties of the NFs shown in FIGS. 2 and 3 may be described inthe following manner. The AMF provides UE-based authentication,authorization, mobility management, etc. A UE even using multiple accesstechnologies is basically connected to a single AMF because the AMF isindependent of the access technologies. The SMF is responsible forsession management and allocates Internet Protocol (IP) addresses toUEs. It also selects and controls the UPF for data transfer. If a UE hasmultiple sessions, different SMFs may be allocated to each session tomanage them individually and possibly provide different functionalitiesper session. The AF provides information on the packet flow to the PCFresponsible for policy control in order to support Quality of Service(QoS). Based on the information, the PCF determines policies aboutmobility and session management to make the AMF and SMF operateproperly. The AUSF supports authentication function for UEs or similarand thus stores data for authentication of UEs or similar while the UDMstores subscription data of the UE. The Data Network (DN), not part ofthe 5G core network, provides Internet access or operator services andsimilar.

An NF may be implemented either as a network element on a dedicatedhardware, as a software instance running on a dedicated hardware, or asa virtualized function instantiated on an appropriate platform, e.g., acloud infrastructure.

FIG. 4

FIG. 4 illustrates the operation of a NF service producer 110-4 (e.g., aSMF or H-SMF) and a NF service consumer (i.e., a NF that consumes aservice of the NF service producer) in accordance with some embodimentof the present disclosure. In the preferred embodiments describedherein, the NF service producer is either a SMF or a H-SMF. Asillustrated, the NF service consumer sends a request to the NF serviceproducer, where the request is associated with a PDU session (e.g., is arequest to create a SM context for the PDU session or a request tocreate the PDU session) (step WT300). The NF service producer sends aresponse to the NF service consumer, where the response includes a GPSIof the PDU session (step WT302). As discussed below, in someembodiments, there are some conditions under which the response WT302may include a GPSI of the PDU session (i.e., a GPSI mapped to orotherwise linked to the PDU session) and some other conditions underwhich the response in WT302 may not include a GPSI of the PDU session.

FIGS. 5 and 6 provide two example implementations of the process of FIG.4 .

FIG. 5

FIG. 5 illustrates a procedure for creating a SM context for a PDUsession in which the SMF provides the GPSI of the PDU session to the NFservice consumer. In General, the Create SM Context service operation isused to create an individual SM context, for a given PDU session, in theSMF, or in the V-SMF for HR roaming scenarios.

The Create SM Context service is used in the following procedures:

-   -   UE requested PDU Session Establishment (see subclause 4.3.2 of        3GPP TS 23.502 [3]);    -   EPS to 5GS Idle mode mobility or handover using N26 interface        (see subclause 4.11.1 of 3GPP TS 23.502 [3]);    -   EPS to 5GS mobility without N26 interface (see subclause        4.11.2.3 3GPP TS 23.502 [3]) (when an existing Packet Data        Network (PDN) connection is moved from EPS to 5GS the existing        PDN connection can be perceived as an existing PDU session by        the AMF, which uses PDU terminology and not PDN terminology);    -   Handover of a PDU session between 3GPP access and non-3GPP        access, when the target AMF does not know the SMF resource        identifier of the SM context used by the source AMF, e.g. when        the target AMF is not in the PLMN of the N3IWF (see subclause        4.9.2.3.2 of 3GPP TS 23.502 [3]), or when the UE is roaming and        the selected N3IWF is in the HPLMN (see subclause 4.9.2.4.2 of        3GPP TS 23.502 [3]);    -   Handover from EPS to 5GC-N3IWF (see subclause 4.11.3.1 of 3GPP        TS 23.502 [3]);    -   Handover from EPC/ePDG to 5GS (see subclause 4.11.4.1 of 3GPP TS        23.502 [3]).        There shall be only one individual SM context per PDU session.

FIG. 5 described in greater detail here discloses a method to create anSM context by using the HTTP POST method. The steps of FIG. 5 are asfollows:

Step XX100: The NF Service Consumer shall send a POST request to theresource representing the SM contexts collection resource of the SMF.The payload body of the POST request shall contain:

-   -   a representation of the individual SM context resource to be        created;    -   the Request Type IE, if it is received from the UE and if the        request refers to an existing PDU session or an existing        Emergency PDU session; the Request Type IE may be included in        the POST request and thus set to Existing PDU Session or set to        Existing Emergency PDU Session respectively, otherwise;    -   the Old PDU Session ID, if it is received from the UE (i.e. for        a PDU session establishment for the SSC mode 3 operation);    -   the indication that the UE is inside or outside of the LADN        (Local Area Data Network) service area, if the DNN corresponds        to a LADN;    -   a subscription for SM context status notification;    -   the servingNfld identifying the serving AMF;    -   trace control and configuration parameters, if trace is to be        activated (see 3GPP TS 32.422 [22]).

For the UE requested PDU Session Establishment procedure in home routedroaming scenario (see subclause 4.3.2.2.2 of 3GPP TS 23.502 [3]), the NFService Consumer shall provide the URI of the Nsmf_PDUSession service ofthe H-SMF in the hSmfUri IE and may provide the URI of theNsmf_PDUSession service of additional H-SMFs. The V-SMF shall try tocreate the PDU session using the hSmfUri IE. If due to communicationfailure on the N16 interface the V-SMF does not receive any responsefrom the H-SMF, then:

-   -   depending on operator policy, the V-SMF may try reaching the        hSmfUri via an alternate path; or    -   if additional H-SMF URI is provided, the V-SMF may try to create        the PDU session on one of the additional H-SMF(s) provided.

The payload body of the POST request may further contain:

-   -   the name of the AMF service to which SM context status        notification are to be sent (see subclause 6.5.2.2 of 3GPP TS        29.500 [4]), encoded in the serviceName attribute.

Step XX102A: On success, “201 Created” shall be returned, the payloadbody of the POST response shall contain the representation describingthe status of the request and the “Location” header shall be present andshall contain the URI of the created resource. The authority and/ordeployment-specific string of the apiRoot of the created resource URImay differ from the authority and/or deployment-specific string of theapiRoot of the request URI received in the POST request.

If the Request Type was received in the request and set toEXISTING_PDU_SESSION or EXISTING_EMERGENCY_PDU_SESSION (e.g. indicatingthat this is a request for an existing PDU session or an existingemergency PDU session), the SMF shall identify the existing PDU sessionor emergency PDU session based on the PDU Session ID; in this case, theSMF shall not create a new SM context but instead update the existing SMcontext and provide the representation of the updated SM context in the“201 Created” response to the NF Service Consumer.

The POST request shall be considered as colliding with an existing SMcontext if:

-   -   it includes the same SUPI, or PEI for an emergency registered UE        without a UICC or without an authenticated SUPI, and the same        PDU Session ID as for an existing SM context; and    -   this is a request to establish a new PDU session, i.e. the        RequestType is absent in the request or is present and set to        INITIAL_REQUEST or INITIAL_EMERGENCY_REQUEST.

A POST request that collides with an existing SM context shall betreated as a request for a new SM context. Before creating the new SMcontext, the SMF should delete the existing SM context locally and anyassociated resources in the UPF and PCF. If the smContextStatusUri ofthe existing SM context differs from the smContextStatusUri received inthe POST request, the SMF shall also send an SM context statusnotification (see subclause 5.2.2.5) targeting the smContextStatusUri ofthe existing SM context to notify the release of the existing SMcontext. For a HR PDU session, if the H-SMF URI in the request isdifferent from the H-SMF URI of the existing PDU session, the V-SMFshould also delete the existing PDU session in the H-SMF by invoking theRelease service operation (see subclause 5.2.2.9).

If the Request Type was received in the request and indicates this is arequest for a new PDU session (i.e. INITIAL_REQUEST) and if the Old PDUSession ID was also included in the request, the SMF shall identify theexisting PDU session to release and to which the new PDU sessionestablishment relates, based on the Old PDU Session ID.

For an existing PDU session, e.g. PDU session moved from another accessor another system, if a GPSI is associated with the PDU session, the SMFshall include the associated GPSI in the response body; For an existingHR PDU session, if the GPSI associated with the PDU session is receivedfrom H-SMF in PDU Session Create response, the SMF shall include it inthe response body.

Step XX102B: If the request does not include the “UE presence in LADNservice area” indication and the SMF determines that the DNN correspondsto a LADN, then the SMF shall consider that the UE is outside of theLADN service area. The SMF shall reject the request if the UE is outsideof the LADN service area.

On failure, or redirection during a UE requested PDU SessionEstablishment, one of the HTTP status code listed in Table 6.1.3.2.3.1-3shall be returned. For a 4xx/5xx response, the message body shallcontain an SmContextCreateError structure, including:

-   -   a ProblemDetails structure with the “cause” attribute set to one        of the application error listed in Table 6.1.3.2.3.1-3;    -   N1 SM information (PDU Session Reject), if the request included        N1 SM information, except if the error prevents the SMF from        generating a response to the UE (e.g. invalid request format).

FIG. 6

FIG. 6 illustrates a procedure for creating a PDU session in which theH-SMF provides the GPSI of the PDU session to the NF service consumer.In general, the Create service operation shall be used to create anindividual PDU session in the H-SMF for HR roaming scenarios. The Createservice operation is used in the following procedures:

-   -   UE requested PDU Session Establishment (see subclause 4.3.2.2.2        of 3GPP TS 23.502 [3]); EPS to 5GS Idle mode mobility or        handover using N26 interface (see subclause 4.11 of 3GPP TS        23.502 [3]);    -   EPS to 5GS mobility without N26 interface (see subclause        4.11.2.3 3GPP TS 23.502 [3] (when an existing PDN connection is        moved from EPS to 5GS the existing PDN connection can be        perceived as an existing PDU session by the AMF, which uses PDU        terminology and not PDN terminology);    -   Handover of a PDU session between 3GPP access and non-3GPP        access, when the target AMF does not know the SMF resource        identifier of the SM context used by the source AMF, e.g. when        the target AMF is not in the PLMN of the N3IWF (see subclause        4.9.2.3.2 of 3GPP TS 23.502 [3]);    -   Handover from EPS to 5GC-N3IWF (see subclause 4.11.3.1 of 3GPP        TS 23.502 [3]);    -   Handover from EPC/ePDG to 5GS (see subclause 4.11.4.1 of 3GPP TS        23.502 [3]).

FIG. 6 described in greater detail here discloses a method for the NFservice consumer (e.g. V-SMF) to create a PDU session by using the HTTPPOST method. As illustrated, the steps of FIG. 6 are as follows.

Step XX200: The NF Service Consumer shall send a POST request to theresource representing the PDU sessions collection resource of the H-SMF.The payload body of the POST request shall contain:

-   -   a representation of the individual PDU session resource to be        created;    -   the Request Type IE, if it is received from the UE and if the        request refers to an existing PDU session or an existing        Emergency PDU session; the Request Type may be included in the        POST request and thus set to Existing PDU Session or set to        Existing Emergency PDU Session respectively, otherwise;    -   the vsmfld IE identifying the serving SMF;    -   the vcnTunnelInfo;    -   the anType;

a URI ({vsmfPduSessionUri}) representing the PDU session resource in theV-SMF, for possible use by the H-SMF to subsequently modify or releasethe PDU session.

As specified in subclause 4.3.2.2.2 of 3GPP TS 23.502 [3], the NFService Consumer shall be able to receive an Update request beforereceiving the Create Response, e.g. for EPS bearer ID allocation (seesubclause 4.11.1.4.1 of 3GPP TS 23.502 [3]) or Secondaryauthorization/authentication (see subclause 4.3.2.3 of 3GPP TS 23.502[3]).

Step XX202A: On success, “201 Created” shall be returned, the payloadbody of the POST response shall contain:

-   -   the representation describing the status of the request;    -   the QoS flow(s) to establish for the PDU session;    -   the epsPdnCnxlnfo IE and, for each EPS bearer, an epsBearerinfo        IE, if the PDU session may be moved to EPS during its lifetime;    -   the “Location” header containing the URI of the created        resource.

The authority and/or deployment-specific string of the apiRoot of thecreated resource URI may differ from the authority and/ordeployment-specific string of the apiRoot of the request URI received inthe POST request.

If an Update Request was sent to the V-SMF before the Create Response,the URI in the “Location” header and in the hsmfPduSessionUri IE of theH-SMF initiated Update Request shall be the same. If the Request Typewas received in the request and set to EXISTING_PDU_SESSION orEXISTING_EMERGENCY_PDU_SESSION (e.g. indicating that this is a requestfor an existing PDU session or an existing emergency PDU session), theSMF shall identify the existing PDU session or emergency PDU sessionbased on the PDU Session ID; in this case, the SMF shall not create anew PDU session or emergency PDU session but instead update the existingPDU session or emergency PDU session and provide the representation ofthe updated PDU session or emergency PDU session in the response to theNF Service Consumer.

The POST request shall be considered as colliding with an existing PDUsession context if:

-   -   it includes the same SUPI, or PEI for an emergency registered UE        without a UICC or without an authenticated SUPI, and the same        PDU Session ID as for an existing PDU session context; and    -   this is a request to establish a new PDU session, i.e. the        RequestType is absent in the request or is present and set to        INITIAL_REQUEST or INITIAL_EMERGENCY_REQUEST.

A POST request that collides with an existing PDU session context shallbe treated as a request for a new PDU session context. Before creatingthe new PDU session context, the SMF should delete the existing PDUsession context locally and any associated resources in the UPF and PCF.If the vsmfPduSessionUri of the existing PDU session context differsfrom the vsmfPduSessionUri received in the POST request, the SMF shallalso send a status notification (see subclause 5.2.2.10) targeting thevsmfPduSessionUri of the existing PDU session context to notify therelease of the existing PDU session context.

If the Request Type was received in the request and indicates this is arequest for a new PDU session (i.e. INITIAL_REQUEST) and if the Old PDUSession ID was also included in the request, the SMF shall identify theexisting PDU session to be released and to which the new PDU sessionestablishment relates, based on the Old PDU Session ID.

The NF Service Consumer shall store any epsPdnCnxlnfo and EPS bearerinformation received from the H-SMF.

If the response received from the H-SMF contains the alwaysOnGrantedattribute set to true, the V-SMF shall check and determine whether thePDU session can be established as an always-on PDU session based onlocal policy.

For existing PDU session, e.g. PDU session moved from another access oranother system, if a GPSI is associated with the PDU session, the SMFshall included it in the response body.

Step XX202B: On failure, or redirection during a UE requested PDUSession Establishment, one of the HTTP status code listed in Table6.1.3.5.3.1-3 shall be returned. Fora 4xx/5xx response, the message bodyshall contain a PduSessionCreateError structure, including:

-   -   a ProblemDetails structure with the “cause” attribute set to one        of the application error listed in Table 6.1.3.5.3.1-3;    -   the n1SmCause IE with the SGSM cause that the H-SMF proposes the        V-SMF to return to the UE, if the request included        n1SmInfoFromUe;    -   n1SmInfoToUe with any information to be sent to the UE (in the        PDU Session Establishment Reject).

Additional information is found in the document(s) provided in theAppendix. The information provided includes an additional description ofthe GPSI for context of the present disclosure.

FIG. 7

FIG. 7 is a schematic block diagram of a network node QQ200 according tosome embodiments of the present disclosure. The network node QQ200 maybe, for example, a NF in the core network QQ110-1 ora network nodeimplementing a NF in the core network QQ110. As illustrated, the networknode QQ200 includes one or more processors QQ204 (e.g., CentralProcessing Units (CPUs), Application Specific Integrated Circuits(ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like),memory QQ206, and a network interface QQ208. The one or more processorsQQ204 are also referred to herein as processing circuitry. The one ormore processors QQ204 operate to provide one or more functions of anetwork node QQ200 (e.g., one or more functions of a NF service consumerQQ210 e.g. such as an AMF or a V-SMF, or a NF service producer QQ220e.g. such as a SMF, or a H-SMF) as described herein. In someembodiments, the function(s) are implemented in software that is stored,e.g., in the memory QQ206 and executed by the one or more processorsQQ204.

FIG. 8

FIG. 8 is a schematic block diagram that illustrates a virtualizedembodiment of the network node QQ200 according to some embodiments ofthe present disclosure. A used herein, a “virtualized” network node isan implementation of the network node QQ200 in which at least a portionof the functionality of the network node QQ200 is implemented as avirtual component(s) (e.g., via a virtual machine(s) executing on aphysical processing node(s) in a network(s)). As illustrated, in thisexample, the network node QQ200 includes one or more processors QQ304(e.g., CPUs, ASICs, FPGAs, and/or the like), memory QQ306, and a networkinterface QQ308. In this example, functions QQ310 of the network nodeQQ200 (e.g., one or more functions of a NF service consumer, a NFservice producer, a SMF, or a H-SMF) described herein are implemented atthe one or more processing nodes QQ300. In some particular embodiments,some or all of the functions QQ310 of the network node QQ200 (e.g., oneor more functions of a NF service consumer, a NF service producer, aSMF, or a H-SMF) described herein are implemented as virtual componentsexecuted by one or more virtual machines implemented in a virtualenvironment(s) hosted by the processing node(s) QQ300.

In some embodiments, a computer program including instructions which,when executed by at least one processor, causes the at least oneprocessor to carry out the functionality of the network node QQ200 oranode (e.g., a processing node QQ300) implementing one or more of thefunctions QQ310 of the network node QQ200 in a virtual environmentaccording to any of the embodiments described herein is provided. Insome embodiments, a carrier comprising the aforementioned computerprogram product is provided. The carrier is one of an electronic signal,an optical signal, a radio signal, or a computer readable storage medium(e.g., a non-transitory computer readable medium such as memory).

FIG. 9

FIG. 9 is a schematic block diagram of the network node QQ200 accordingto some other embodiments of the present disclosure. The network nodeQQ200 includes one or more modules QQ400, each of which is implementedin software. The module(s) QQ400 provide the functionality of thenetwork node QQ200 (e.g., one or more functions of a NF service consumerQQ210 such as e.g. an AMF or a V-SMF, or a NF service producer QQ220such as e.g. a SMF, or a H-SMF) described herein. This discussion isequally applicable to the processing node QQ300 of Figure QQ3 where themodules QQ400 may be implemented at one of the processing nodes QQ300 ordistributed across multiple processing nodes QQ300 and/or distributedacross the processing node(s) QQ300 and the control system QQ202.

While processes in the figures may show a particular order of operationsperformed by certain embodiments of the present disclosure, it should beunderstood that such order is exemplary (e.g., alternative embodimentsmay perform the operations in a different order, combine certainoperations, overlap certain operations, etc.).

Some embodiments described above may be summarized in the followingmanner:

1. A method performed by a network function (NF) service consumer, themethod comprising:

-   -   sending (WT300, XX100, XX200), for a SMF or H-SMF, a request        related to a PDU session; and    -   receiving (WT302, XX102A, XX202A), from the SMF or H-SMF, a        response comprising a GPSI of the PDU session.

2. The method of embodiment 1 further comprising receiving (XX102B,XX202B) an error message if the request is not granted.

3. The method of embodiment 1 wherein the request is a request to createan SM context for the PDU session.

4. The method of embodiment 1 wherein the request is a request to createthe PDU session.

5. The method of embodiments 3 and 4 wherein if the GPSI is associatedwith the PDU session, the GPSI is included a body of the response.

6. A method performed by a SMF or H-SMF, the method comprising:

-   -   receiving (WT300, XX100, XX200), from a NF service consumer, a        request related to a PDU session; and    -   sending (WT302, XX102A, XX202A), to the NF service consumer, a        response comprising a GPSI of the PDU session.

7. The method of embodiment 6 further comprising sending (XX102B,XX202B) an error message if the request is not granted.

8. The method of embodiment 6 wherein the request is a request to createan SM context.

9. The method of embodiment 6 wherein the request is a request to createa PDU session.

10. The method of embodiment 6, 8, or 9 wherein, if a GPSI is associatedwith the PDU session, the GPSI is in a body of the response.

11. A NF service consumer adapted to perform the method of any one ofembodiments 1 to 5.

12. A network node for implementing a NF service consumer, the networknode comprising:

a network interface; and

processing circuitry associated with the network interface, theprocessing circuitry configured to cause the network node to implementthe NF service consumer, the NF service consumer adapted to perform themethod of any one of embodiments 1 to 5.

13. A SMF or H-SMF adapted to perform the method of any one ofembodiments 6 to 10.

14. A network node for implementing a SMF or H-SMF, the network nodecomprising:

a network interface; and

processing circuitry associated with the network interface, theprocessing circuitry configured to cause the network node to implementthe SMF or H-SMF, the SMF or H-SMF adapted to perform the method of anyone of embodiments 6 to 10.

Some further embodiments described above may be summarized in thefollowing manner:

1. A method by an Access and Mobility Management Function, AMF, node,(120-4) operative in a Fifth Generation System, 5GS, (100-1, 100-2,100-3) that comprises a User Equipment, UE, (112) associated with aSubscriber Permanent Identifier, SUPI, that is associated withsubscription data of the UE, the method comprises:

-   -   sending (WT300, XX100, XX200) towards a Session Management        Function, SMF, node (110-4), a request relating to a Protocol        Data Unit, PDU, Session of the UE and comprising a Request Type        that is set to Existing PDU Session; and    -   receiving (WT302, XX102A, XX202A), from the SMF node, a response        comprising a Generic Public Subscription Identifier, GPSI, of        the PDU session, which GPSI is associated with the SUPI and        which GPSI is to be used in networks outside the 5GS for        addressing the subscription data of the UE.

2. The method of embodiment 1 wherein the PDU session is moved fromanother system to the 5GS.

3. The method of embodiment 1 wherein the PDU session is moved from anEvolved Packet Core, EPS, system to the 5GS.

4. The method of any one of embodiment 1-3 wherein the request is arequest to create an SM context for the existing PDU session.

5. The method of any one of embodiment 1-4 wherein if the GPSI isassociated with the existing PDU session, the GPSI is included a body ofthe response.

6. A method by a Session Management Function, SMF, node (110-4)operative in a Fifth Generation System, 5GS, (100-1, 100-2, 100-3) thatcomprises a User Equipment, UE, (112) associated with a SubscriberPermanent Identifier, SUPI, that is associated with subscription data ofthe UE, the method comprises:

-   -   receiving (WT300, XX100, XX200), from an Access and Mobility        Management Function, AMF, node, (120-4), a request relating to a        Protocol Data Unit, PDU, Session of the UE and comprising a        Request Type that is set to Existing PDU Session; and    -   sending (WT302, XX102A, XX202A), towards the AMF node, a        response comprising a Generic Public

Subscription Identifier, GPSI, of the PDU session, which GPSI isassociated with the SUPI and which GPSI is to be used in networksoutside the 5GS for addressing the subscription data of the UE.

7. The method of embodiment 6 wherein the PDU session is moved fromanother system to the 5GS.

8. The method of embodiment 6 wherein the PDU session is moved from anEvolved Packet Core, EPS, system to the 5GS.

9. The method of any one of embodiment 6-8 wherein the request is arequest to create an SM context.

10. The method of any one of embodiment 6-9 wherein, if a GPSI isassociated with the existing PDU session, the GPSI is in a body of theresponse.

11. A network node implementing an Access and Mobility ManagementFunction, AMF, node (120-4) configured to be operative in a FifthGeneration System, 5GS, (100-1, 100-2, 100-39) that comprises a User

Equipment, UE, (112) associated with a Subscriber Permanent Identifier,SUPI, that is associated with subscription data of the UE, the AMF nodecomprising:

a network interface (QQ208, Namf); and

processing circuitry (QQ204) associated with the network interface, theprocessing circuitry configured to cause the network node to implementthe AMF node, the AMF node adapted to:

-   -   send (WT300, XX100, XX200), towards a Session Management        Function, SMF, node (110-4), a request relating to a Protocol        Data Unit, PDU, Session of the UE and comprising a Request Type        that is set to Existing PDU Session; and    -   receive (WT302, XX102A, XX202A), from the SMF node, a response        comprising a Generic Public Subscription Identifier, GPSI, of        the PDU session, which GPSI is associated with the SUPI and        which GPSI is to be used in networks outside the 5GS for        addressing the subscription data of the UE.

12. A network node implementing a Session Management Function, SMF, node(110-4) configured to be operative in a Fifth Generation System, 5GS,(100-1, 100-2, 100-39) that comprises a User Equipment, UE, (112)associated with a Subscriber Permanent Identifier, SUPI, that isassociated with subscription data of the UE, the network nodecomprising:

a network interface (QQ208, Nsmf); and

processing circuitry (QQ204) associated with the network interface, theprocessing circuitry configured to cause the network node to implementthe SMF node, the SMF node adapted to:

-   -   receive (WT300, XX100, XX200), from an Access and Mobility        Management Function, AMF, node, (120-4), a request relating to a        Protocol Data Unit, PDU, Session of the UE and comprising a        Request Type that is set to Existing PDU Session; and    -   send (WT302, XX102A, XX202A), to the AMF node, a response        comprising a GPSI of the existing PDU session, which GPSI is        associated with the SUPI and which GPSI is to be used in        networks outside the 5GS for addressing the subscription data of        the UE.

Abbreviations

At least some of the following abbreviations may be used in thisdisclosure. If there is an inconsistency between abbreviations,preference should be given to how it is used above. If listed multipletimes below, the first listing should be preferred over any subsequentlisting(s).

-   -   2G Second Generation    -   3G Third Generation    -   3GPP Third Generation Partnership Project    -   4G Fourth Generation    -   5G Fifth Generation    -   AF Application Function    -   AMF Access and Mobility Management Function    -   AN Access Network    -   AP Access Point    -   AUSF Authentication Server Function    -   BS Base Station    -   BSC Base Station Controller    -   BTS Base Transceiver Station    -   CDMA Code Division Multiple Access    -   CGI Cell Global Identifier    -   DL Downlink    -   DN Data Network    -   eNB Enhanced or Evolved Node B    -   E-UTRA Evolved Universal Terrestrial Radio Access    -   E-UTRAN Evolved Universal Terrestrial Radio Access Network    -   gNB New Radio Base Station    -   GPSI Generic Public Subscription Identifier    -   HO Handover    -   IP Internet Protocol    -   LAN Local Area Network    -   LTE Long Term Evolution    -   MAC Medium Access Control    -   MME Mobility Management Entity    -   MSC Mobile Switching Center    -   MTC Machine Type Communication    -   NEF Network Exposure Function    -   NF Network Function    -   NFV Network Function Virtualization    -   NR New Radio    -   NRF Network Repository Function    -   NSSF Network Slice Selection Function    -   PCF Policy Control Function    -   PDU Protocol Data Unit    -   P-GW Packet Data Network Gateway    -   PLMN Public Land Mobile Network    -   QoS Quality of Service    -   RAN Radio Access Network    -   RAT Radio Access Technology    -   RNC Radio Network Controller    -   SCEF Service Capability Exposure Function    -   S-GW Serving Gateway    -   SMF Session Management Function    -   TCP Transmission Control Protocol    -   UDM Unified Data Management    -   UE User Equipment    -   UL Uplink    -   UMTS Universal Mobile Telecommunications System    -   USIM Universal Subscriber Identity Module

1. A method by an Access and Mobility Management Function, AMF, node,operative in a Fifth Generation System, 5GS, that comprises a UserEquipment, UE, associated with a Subscriber Permanent Identifier, SUPI,that is associated with subscription data of the UE, the methodcomprises: sending towards a Session Management Function, SMF, node, arequest relating to a Protocol Data Unit, PDU, Session of the UE andcomprising a Request Type that is set to Existing PDU Session; andreceiving, from the SMF node, a response comprising a Generic PublicSubscription Identifier, GPSI, of the PDU session, which GPSI isassociated with the SUPI and which GPSI is to be used in networksoutside the 5GS for addressing the subscription data of the UE.
 2. Themethod of claim 1 wherein the PDU session is moved from another systemto the 5GS.
 3. The method of claim 1 wherein the PDU session is movedfrom an Evolved Packet Core, EPS, system to the 5GS.
 4. The method ofclaim 1 wherein the request is a request to create an SM context for theexisting PDU session.
 5. The method of claim 1 wherein if the GPSI isassociated with the existing PDU session, the GPSI is included a body ofthe response.
 6. A method by a Session Management Function, SMF, nodeoperative in a Fifth Generation System, 5GS, that comprises a UserEquipment, UE, associated with a Subscriber Permanent Identifier, SUPI,that is associated with subscription data of the UE, the methodcomprises: receiving, from an Access and Mobility Management Function,AMF, node, a request relating to a Protocol Data Unit, PDU, Session ofthe UE and comprising a Request Type that is set to Existing PDUSession; and sending, towards the AMF node, a response comprising aGeneric Public Subscription Identifier, GPSI, of the PDU session, whichGPSI is associated with the SUPI and which GPSI is to be used innetworks outside the 5GS for addressing the subscription data of the UE.7. The method of claim 6 wherein the PDU session is moved from anothersystem to the 5GS.
 8. The method of claim 6 wherein the PDU session ismoved from an Evolved Packet Core, EPS, system to the 5GS.
 9. The methodof claim 6 wherein the request is a request to create an SM context. 10.The method of claim 6 wherein, if a GPSI is associated with the existingPDU session, the GPSI is in a body of the response.
 11. A network nodeimplementing an Access and Mobility Management Function, AMF, nodeconfigured to be operative in a Fifth Generation System, 5GS, thatcomprises a User Equipment, UE, associated with a Subscriber PermanentIdentifier, SUPI, that is associated with subscription data of the UE,the AMF node comprising: a network interface; and processing circuitryassociated with the network interface, the processing circuitryconfigured to cause the network node to implement the AMF node, the AMFnode adapted to: send, towards a Session Management Function, SMF, node,a request relating to a Protocol Data Unit, PDU, Session of the UE andcomprising a Request Type that is set to Existing PDU Session; andreceive, from the SMF node, a response comprising a Generic PublicSubscription Identifier, GPSI, of the PDU session, which GPSI isassociated with the SUPI and which GPSI is to be used in networksoutside the 5GS for addressing the subscription data of the UE.
 12. Anetwork node implementing a Session Management Function, SMF, nodeconfigured to be operative in a Fifth Generation System, 5GS, thatcomprises a User Equipment, UE, associated with a Subscriber PermanentIdentifier, SUPI, that is associated with subscription data of the UE,the network node comprising: a network interface; and processingcircuitry associated with the network interface, the processingcircuitry configured to cause the network node to implement the SMFnode, the SMF node adapted to: receive, from an Access and MobilityManagement Function, AMF, node, a request relating to a Protocol DataUnit, PDU, Session of the UE and comprising a Request Type that is setto Existing PDU Session; and send, to the AMF node, a responsecomprising a GPSI of the existing PDU session, which GPSI is associatedwith the SUPI and which GPSI is to be used in networks outside the 5GSfor addressing the subscription data of the UE.